Introduce dual-track course structure and add day/evening course maps - #12
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Description
README.mdto describe the dual-track course intent, add a selection table for class routes, and adjust the main navigation.courses/README.mdto define the "one repository, two tracks" architecture, maintenance rules, and naming/semester guidelines.courses/day/README.mdwith the day-track syllabus, recommended unit order, project minimums, and support items to be added.courses/evening/README.mdwith the evening-track syllabus emphasizing Python→API→cloud workflow, unit sequence, assessment checkpoints, and grading guidance.docs/README.mdto include links to the new course map pages and reorganize the docs index accordingly.Testing
Codex Task